Skip to content

upgrade: luajit to version 2.1-20240815 #416

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Dec 18, 2024
Merged

upgrade: luajit to version 2.1-20240815 #416

merged 3 commits into from
Dec 18, 2024

Conversation

@Revolyssup
Copy link
Contributor

@Revolyssup Revolyssup commented Dec 17, 2024

In LuaJit version 2.1-20240815, some performance and security issues have been fixed. OpenResty version 1.27.1.1 has already used this version, and we hope that the enterprise version will also be upgraded to this version.

LuaJIT updated to 2.1-20240815 with various optimizations and bugfixes:

Improved error handling and stack overflow management

Enhanced cross-32/64 bit and deterministic bytecode generation

Disabled hash computation optimization in the OpenResty branch due to potential severe performance degradation (CVE-2024-39702). This issue only exists in the OpenResty branch (agentzh-v2.1) and not in upstream LuaJIT. We thank Zhongwei Yao from Kong Inc. for reporting this issue.

@Revolyssup
Copy link
Contributor Author

Revolyssup commented Dec 17, 2024

EE CI passing with this commit. Ref: https://github.com/api7/api7-ee-3-gateway/pull/696

membphis
membphis reviewed Dec 18, 2024
View reviewed changes
@Revolyssup Revolyssup merged commit cf5653b into api7:release/api7ee-runtime Dec 18, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@membphis membphis membphis approved these changes

@nic-6443 nic-6443 Awaiting requested review from nic-6443

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Revolyssup @membphis